Sharing information between tenants of a multi-tenant database

ABSTRACT

In a method, system, and computer-readable medium having instructions for sharing information between tenants of a multi-tenant database, information is received on a connection between a first tenant of a multi-tenant database and a second tenant and the connection has information on a scope of data from the first tenant shared with the second tenant, data is allowed for a record of the first tenant to be accessible to the second tenant in accordance with the connection, information is received on a file related to the record of the first tenant, and data is allowed from the file to be accessible to the second tenant in accordance with the connection.

CROSS REFERENCE TO RELATED PATENTS

This application claims the benefit of U.S. Provisional PatentApplication 61/351,642 entitled “METHODS AND SYSTEMS FOR SHARINGINFORMATION BETWEEN TENANTS OF A MULTI-TENANT DATABASE ENVIRONMENT,”filed Jun. 4, 2010, Kuruganti et al., (Attorney Docket No. SALEP0024),the entire contents of which are incorporated herein by reference.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

FIELD OF THE INVENTION

The current invention relates generally to sharing information in adatabase network system.

BACKGROUND

The subject matter discussed in the background section should not beassumed to be prior art merely as a result of its mention in thebackground section. Similarly, a problem mentioned in the backgroundsection or associated with the subject matter of the background sectionshould not be assumed to have been previously recognized in the priorart. The subject matter in the background section merely representsdifferent approaches, which in and of themselves may also be inventions.

In conventional database systems, users access their data resources inone logical database. A user of such a conventional system typicallyretrieves data from and stores data on the system using the user's ownsystems. A user system might remotely access one of a plurality ofserver systems that might in turn access the database system. Dataretrieval from the system might include the issuance of a query from theuser system to the database system. The database system might processthe request for information received in the query and send to the usersystem information relevant to the request. The secure retrieval ofaccurate information and subsequent delivery of this information to theuser system has been and continues to be a goal of administrators ofdatabase systems.

Unfortunately, conventional database approaches might limit retrieval ofinformation from the database system to users that have authorization toaccess data in the particular database system. Conventional databasesystems do not provide a mechanism for sharing data in a particulardatabase system to users that do not have authorization for theparticular database system. Accordingly, it is desirable to providetechniques enabling secure sharing of information from the databasesystem of the database system.

BRIEF SUMMARY

In accordance with embodiments, there are provided mechanisms andmethods for sharing information between tenants in a multi-tenantdatabase system.

In an embodiment and by way of example, a method for sharing informationbetween tenants in a multi-tenant database system is provided. In amethod, system, and computer-readable medium having instructions forsharing information between tenants of a multi-tenant database,information is received on a connection between a first tenant of amulti-tenant database and a second tenant and the connection hasinformation on a scope of data from the first tenant shared with thesecond tenant, data is allowed for a record of the first tenant to beaccessible to the second tenant in accordance with the connection,information is received on a file related to the record of the firsttenant, and data is allowed from the file to be accessible to the secondtenant in accordance with the connection.

While one or more implementations and techniques are described withreference to an embodiment in which sharing information between tenantsin a multi-tenant database system environment is implemented in a systemhaving an application server providing a front end for an on-demanddatabase service capable of supporting multiple tenants, the one or moreimplementations and techniques are not limited to multi-tenant databasesnor deployment on application servers. Embodiments may be practicedusing other database architectures, i.e., ORACLE®, DB2® by IBM and thelike without departing from the scope of the embodiments claimed.

Any of the above embodiments may be used alone or together with oneanother in any combination. The one or more implementations encompassedwithin this specification may also include embodiments that are onlypartially mentioned or alluded to or are not mentioned or alluded to atall in this brief summary or in the abstract. Although variousembodiments may have been motivated by various deficiencies with theprior art, which may be discussed or alluded to in one or more places inthe specification, the embodiments do not necessarily address any ofthese deficiencies. In other words, different embodiments may addressdifferent deficiencies that may be discussed in the specification. Someembodiments may only partially address some deficiencies or just onedeficiency that may be discussed in the specification, and someembodiments may not address any of these deficiencies.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following drawings like reference numbers are used to refer tolike elements. Although the following figures depict various examples ofthe invention, the invention is not limited to the examples depicted inthe figures.

FIG. 1 illustrates an example of a simplified flow diagram for sharinginformation between tenants in a multi-tenant database system.

FIG. 2A illustrates an example of a user interface for sharinginformation between tenants in a multi-tenant database system.

FIG. 2B illustrates an example of a user interface for sharinginformation between tenants in a multi-tenant database system.

FIG. 3 illustrates an example of a user interface for establishing aconnection between tenants for sharing information between tenants in amulti-tenant database system.

FIG. 4 illustrates an example of flow diagram for sharing informationbetween tenants in a multi-tenant database system.

FIG. 5A illustrates an example of a user interface for sharinginformation between tenants in a multi-tenant database system.

FIG. 5B illustrates an example of a user interface for sharinginformation between tenants in a multi-tenant database system.

FIG. 5C illustrates an example of a user interface for sharinginformation between tenants in a multi-tenant database system.

FIG. 5D illustrates an example of a user interface for sharinginformation between tenants in a multi-tenant database system.

FIG. 6 illustrates a block diagram of an example of an environmentwherein an on-demand database service might be used; and

FIG. 7 illustrates a block diagram of an embodiment of elements of FIG.6 and various possible interconnections between these elements.

DETAILED DESCRIPTION General Overview

Systems, computer readable mediums, and methods are provided for sharinginformation between tenants in a multi-tenant database. Tenant data,typically, is arranged in a multi-tenant database such that data of onetenant is kept logically separate from that of other tenants so onetenant does not have access to another tenant's data, unless such datais expressly shared. It may be desirable for one or more tenants of amulti-tenant database to share data or information with other tenantsand/or one or more users of another database system. In one or moreembodiments, users of a first tenant can specify the data to be sharedwith one or more users at a second tenant in a multi-tenant database.

The tenant may have a connection with one or more other tenants thatserves a contract to allow sharing of information or data betweentenants. The connection may indicate the scope of the data sharedbetween one or more users of a first and a second tenant. Tenants and/orusers of a multi-tenant database system may expressly give permission toshare data with users of another tenant. For example, a user of a firsttenant database system may give permission to provide a set of relateddata to one or more users for other tenants in a multi-tenant databasesystem. In another example, a user of a first tenant may specify toshare a record with a user of a second tenant, and all related data tothe shared record. Continuing with the example, the parent and childrecords of the shared record of the first tenant may be shared with thesecond tenant.

Data related or associated with a shared record may be shared betweentenants of a multi-tenant database system. In one or more embodiments, afile from a first tenant may be securely shared with a second tenant.The file may be associated with a shared record for a first tenant andthe file may be shared with the second tenant in accordance with theconnection between the first and second tenant.

As used herein, the term multi-tenant database system refers to thosesystems in which various elements of hardware and software of thedatabase system may be shared by one or more customers/tenants. Forexample, a given application server may simultaneously process requestsfor a great number of customers/tenants, and a given database table maystore rows for a potentially much greater number of customers.

Next, systems, computer readable mediums with instructions, and methodsfor sharing information between tenants in a multi-tenant database willbe described with reference to example embodiments. In the followingexamples, one or more implementations are illustrated for optimizingqueries. Clearly, in alternate implementations, the illustratedprocesses and process steps may be combined into fewer steps, dividedinto more steps, and/or performed in a different sequence.

FIG. 1 illustrates an example of a simplified flow diagram for sharinginformation between tenants in a multi-tenant database system. Data maybe received for a record of the first tenant (100). The data may bereceived by the database system from a user using an ApplicationProgramming Interface (API), a graphical user interface, a SQL query,and/or any other user interface for software. The data may be receivedfor a record of a database table for a tenant in a multi-tenantdatabase. In a preferred embodiment, data may be received for recordsfor entry in database tables for entities used with CustomerRelationship Management(CRM) software, including, but not limited to,Cases, Contacts, Accounts, Opportunities, Tasks, Activities, Notes,Attachments, Comments, Custom tenant entities, and/or any other databaseentities.

The tenant may have data stored in a multi-tenant database that islogically separate from other tenants of the multi-tenant database. In apreferred embodiment, a tenant may have a tenant id number (e.g. a key)to identify the tenant data for retrieval and entry into themulti-tenant database. For example, a record for a tenant (e.g. a Case,a Note, etc.) may have a tenant id associated with the record toindicate that the record is for a tenant of multi-tenant databasesystem.

Upon entry of the received data, a check may be performed to determinewhether the received data may be shared with one or more tenants. Forexample, a check may be performed by accessing one or more databasetables to determine if a record of a first tenant is shared with asecond tenant. Continuing with the example, a shared record may haveattribute (e.g. a column in the database table for the record) thatindicates the record may be shared with other tenants.

In an embodiment, the sharing of data may be perceived as a pushtechnology. For example, upon receipt of the new data, the server maypush the data to the second tenant. In another embodiment, the sharingof data may be perceived as pull technology and the server may await aspecific request to send data to a second tenant. For example, thesecond tenant may request the new data for the first tenant from theserver.

In one or more embodiments, a trigger may be used to perform a checkupon entry of the data in a database table. The trigger may be adatabase trigger with functionality provided by a databaseimplementation and/or the trigger may be a method/function provided bythe tenant and/or the on-demand database service. A trigger may cause acheck to be performed to determine whether one or more tenants have aconnection (e.g. an agreement to share data) upon entry of data to adatabase table.

Information may be received on a connection between a first tenant and asecond tenant (102). The connection may indicate whether the receiveddata may be shared with a second tenant. The connection may indicate thescope of the data shared with the second tenant, including, but notlimited to, the hierarchical relationships to shared data (e.g. a sharedrecord) that are permitted to be shared and the public records relatedto the shared record. For example, the connection may provide that entryof a Case record should cause at least a portion of related records tothe Case (e.g. Account, Notes, Attachments, other Cases, Comments, etc)to be shared with the second tenant, and other related records, such asOpportunities and Leads may not be shared. Continuing with the example,a Case record may indicate a problem with a particular product, andrelated Cases and Comments to the Case record may indicate the status ofthe handling of the problem by a reseller (e.g. a first tenant) and asupplier (e.g. a second tenant).

In another example, the Case record may have related public Case recordsfrom a third tenant that may be shared with the second tenant.Continuing with the example, the Case record may indicate a particularproblem with an Account and/or a Product that may be shared among one ormore tenants.

The connection may be established after notification to both tenants andauthentication that the notification on desire to connect/accept aconnection came from the respective tenants. The connection may bemanaged to specify the tenants that share data and the scope of theshared data. An implementation of a connection is described in U.S.patent application Ser. No. 12/145,325, entitled “Sharing Data BetweenSubscribers of a Multi-Tenant Database Service,” filed on Jun. 24, 2008,which is incorporated herein by reference, and U.S. patent applicationSer. No. 12/437,459, entitled “Sharing Tenant Information Utilizing aMulti-Tenant On-Demand Database Service,” filed on May 7, 2009, which isincorporated herein by reference.

Data for the record of the first tenant may be allowed to be accessibleto the second tenant (104). The data for the record of the first tenantmay be sent to the second tenant in accordance with the connection. Forexample, the received data for the record may be sent to the secondtenant for entry into a record for a database table for the secondtenant. A new record for a table at the second tenant may be createdand/or an existing record of the second tenant may be used for thereceived data.

In a preferred embodiment, the received data, designated as data toshare in accordance with the connection for the tenants, may be placedin a queue for processing by a process that executes in the backgroundfor the on-demand multi-tenant database service. In one or moreembodiments, the queue may be implemented as a table with fleetingrecords, a list, and/or any other data structure. A notification may beplaced on the queue with the received data, a record for the second,and/or any other type of method for communicating to share the receiveddata.

Information may be received on a file related to the record of the firsttenant (106). The received data may be a file attachment and/or data fora record associated with a file attachment. For example, the receiveddata may be for a Case that has an attribute with a file name and filepath for an attachment at the first tenant. In another example, the Casemay have a related Comment (e.g. a child record of a Case record, aComment of a parent Case record to the Case, etc.) with a fileattachment.

In another example, the filepath/filename may be an attribute/columnvalue for a related record to the record with the shared data.Continuing with the example, the file may be a file with a history ofcorrespondence between a reseller and a customer, and the file may beshared when the Case involving the customer is shared with anothertenant. The record that may be shared between tenants may have columnsthat indicate the related records and/or files.

The connection may indicate if the file may be shared with the secondtenant. For example, the attachment file may be viewed as a child recordto a Case (e.g. a shared record) and the connection for the Case recordmay indicate that all related records to the Case may be shared with thesecond tenant. In another example, the connection may specify if fileattachments may be shared between tenants for the connection.

The data from the file may be allowed to be accessible to the secondtenant (108). The data from the file may be made accessible to thesecond tenant with the following implementations, including, but notlimited to, providing a filepath/filename, copying the contents of thefile to a record, providing a resource locator for accessing the file,sending a notification with the file to one or more users, and/or anyother method for sharing the file with a second tenant. In one or moreembodiments, a record with the contents of the file may be placed on aqueue for processing by a background process for the on-demandmulti-tenant database service. Continuing with the example, the newrecord with the contents of the file may be sent to the second tenant bythe background process to be entered in to the database for the secondtenant. The data from the file may be copied to a record for entry intoa database table at the second tenant. The file may be cleaned orstripped of any harmful code before being sent to the second tenant. Inanother embodiment, the uniform resource locator (URL) may be providedto the second tenant to access the file as a column value in a databasetable.

In an embodiment, the file may provide information on one or morerecords in a database table for the first tenant. For example, the filethat is shared may be a WSDL file describing database tables and sharedcolumns of database tables of a first tenant that may be shared with asecond tenant, and the WSDL may be used to replicate a hierarchy at thefirst tenant for the shared records at the second tenant. In anotherexample, the file may provide the hierarchical relationship for relatedrecords at the first tenant and/or mapping information between thetenants.

In one or more embodiments, a user of the second tenant may specifywhether to accept the record with the file attachment. For example, theuser of the second tenant may indicate that all shared records and fileattachments may be entered automatically in the database for the secondtenant in a similar hierarchical structure to the first tenant. The userof the second tenant may specify exactly how the shared records andattachments may map to the database tables of the second tenant. Inanother embodiment, the user of the second tenant may assign their ownassignment rules and/or determine where the shared record and/or fileattachment may fit into their database system upon acceptance of theshared record and/or file attachment.

FIG. 2A illustrates an example of a user interface for sharinginformation between tenants in a multi-tenant database system. FIG. 2Aprovides a user interface for a Note record of a first tenant that maybe shared with a second tenant. The example of the user interface inFIG. 2A provides an interface for editing the Note 200 record. The userinterface provides the ability to ‘Save’ the record in the database,‘Cancel’ editing the record, ‘Spell Check’ for the record, indicatewhether the record is ‘Private’ 202, enter a ‘Title’ for the Noterecord, and enter the ‘Body’ contents of the Note. One or more of thefields for the Note may be published to a record of the second tenant ifthe record is designated to be shared between the first and secondtenant in accordance with the connection between the tenants.

In a preferred embodiment, the Notes may be child records of otherrecords, including, but not limited to, Leads, Opportunities, Accounts,Contacts, Products, Cases, and Custom entities for a tenant. Bydesignating the Note as ‘Private’ 202, the Note may not be shared withthe second tenant even though the connection between the tenants mayindicate that Notes may be shared. One or more attributes of the Noterecord at the first tenant may not be shared and/or accessible to thesecond tenant. In an embodiment, a Note may be designated to ‘Share withConnections’ with the user interface, and the Note may then be sharedwith a tenant in accordance with the connection for the first and secondtenant.

In one or more embodiments, the user may need to explicitly indicatethat the record may be shared with the second tenant. For example, aparent record of the Note record may be shared with the second tenant,but the Note record may have an attribute that indicates the record maynot be shared with connections and the Note may not be shared. In apreferred embodiment, Notes may be shared with a second tenant when theparent record is shared, Notes are designated to be shared for theconnection, and the Note is not private.

FIG. 2B illustrates an example of a user interface for sharinginformation between tenants in a multi-tenant database system. FIG. 2Bprovides a user interface for an Attachment record of a first tenantthat may be shared with a second tenant. The example of the userinterface in FIG. 2B provides an interface for editing the Attachmentrecord. The user interface provides the ability to ‘Save’ the record inthe database, ‘Cancel’ editing the record, indicate whether the recordis ‘Private’ 204, enter a ‘File Name’ for the Attachment record, andenter the ‘FileName’ for the Attachment, and indicate whether to ‘Sharewith Connections’ 206. For example, if the Attachment is marked‘Private’ 204 with the user interface, then the Attachment may not beshared even if a parent record is shared. Continuing with the example,if the Attachment record is marked to ‘Share with Connections’ and theAttachment record is not marked private, then the Attachment may beshared with a second tenant.

In a preferred embodiment, the Attachment is shared as a child recordwhen the parent record is shared. The ‘File Name’ may associate a filename and a file path (e.g. an attribute or field in an Attachmentrecord) with the Attachment record. In one or more embodiments, the filecontents are shared with the second tenant and the filename/file path atthe first tenant may not be shared with the second tenant. In anotherembodiment, the filename/file path may be a URL and publicly accessibleso the filename/file path attribute of a shared record may be sharedwith the second tenant.

FIG. 3 illustrates an example of a user interface for establishing aconnection between tenants for sharing information between tenants in amulti-tenant database system. FIG. 3 provides a user interface formanaging connections between a first tenant and a second tenant. Theexample of the user interface in FIG. 3 provides an interface forediting connections and sharing connections for a record. In FIG. 3, therelated records for a record and a connection may be forwarded byselecting ‘Forward Related Records’ 300, the child records for aconnection may be forwarded by selecting ‘Forward Child Records’ 302,and email notifications to record owners and/or tenants may be selectedwith ‘Send Notification Email’ 304. For example, ‘Shared Connection 3’306 is a connection between one or more tenants and ‘Forward RelatedRecords’ 300 has been selected for the connection. Continuing with theexample, if an Account record is shared with Connection 3, then a Casemay be forwarded for ‘Shared Connection 3’ as a child record of theAccount record for the first tenant and shared with the second tenant,and a Case record that is a parent record of the shared Case record maybe shared with the second tenant.

In another example, a user for a first tenant may select ‘Forward ChildRecords’ and the child record for the shared record may be shared. Forexample, if a Case record is shared then the child records for the Case(e.g. Comments, other Cases, etc.) may be shared but the parent recordto the Case (e.g. Account) may not be shared.

A user may specify whether to ‘Send Email Notifications’ 304. Forexample, an email notification may be sent to users of a first tenantand/or users of a second tenant to indicate that a record is sharedand/or going to be shared. In an embodiment, the email notification mayallow the user to decide whether to proceed with sharing a record and/orrelated records to a shared record.

FIG. 4 illustrates an example of flow diagram for sharing informationbetween tenants in a multi-tenant database system. Data may be receivedfor a first tenant (400). Data for a first tenant of a multi-tenantdatabase system may be entered using a user interface, a databaserequest, and/or any other method for sending data to a database system.The data may be received for entry of a new record or entry of data intoan existing record of a database table for a first tenant in thedatabase system. In a preferred embodiment, the records may be enteredin database tables for CRM entities, including, but not limited to,Cases, Contacts, Accounts, Opportunities, Tasks, Activities, Notes,Attachments, Comments, Custom entities, and/or any other databaseentities. The records may be related and have hierarchical relationshipsbetween them. For example, a Case record may be a parent records for aComment record, and the Case record may be a child of an Account oranother Case record.

In one or more embodiments, the data received may be a file and/orinformation on a file location associated with a record. The file may beassociated with a record as an attribute of the record (e.g. a file nameas an attribute) and/or the contents of the file may be inserted into arelated record to the record (e.g. a text field of a child record).

In another embodiment, the data received may be for a record that isassociated with a file (e.g. a record related to an Attachment, a recordrelated to a record with a file). The record associated with the fileattachment may be shared, and the file attachment may be shared with thesecond tenant in accordance with the connection between the tenants.

Information may be retrieved on a connection between the first tenantand a second tenant (402). A connection and/or agreement may be reachedbetween tenants in a multi-tenant database system to share at least aportion of data from the first tenant. The connection may be establishedby sending a notification requesting to share and receiving a responsethat permits sharing of data between the tenants. The user sending thenotification and the user sending the response regarding establishing aconnection between the tenants may be authenticated before data isshared between the tenants. An implementation of a connection isdescribed in U.S. patent application Ser. No. 12/145,325, entitled“Sharing Data Between Subscribers of a Multi-Tenant Database Service,”filed on Jun. 24, 2008, which is incorporated herein by reference, andU.S. patent application Ser. No. 12/437,459, entitled “Sharing TenantInformation Utilizing a Multi-Tenant On-Demand Database Service,” filedon May 7, 2009, which is incorporated herein by reference. Theconnection may be viewed as a metadata contractual agreement between thetenants.

A determination may be made as to whether the data entered involves ashared record (404). The tenants may specify the shared data that may bereplicated and synchronized between the tenants with the connection. Forexample, a first tenant may specify that all data related to aparticular Account record may be shared between the tenants. In anotherexample, the first tenant may indicate that a Case record and allrelated records (e.g. child and parent records) for the case may beshared with the second tenant. The first tenant may share all recordsand/or a portion of one or more records for the first tenant.

In an embodiment, a user may utilize a user interface such asillustrated in FIG. 3 to associate a connection with a record. Byassociating the record with a connection, the record may be a sharedrecord between the tenants. As illustrated in FIG. 3, the scope ofsharing for a particular shared record and related records of the sharedmay be specified for the connection between the tenants on a recordbasis. Those skilled in the art will recognize that the scope of sharingmay be applied for one or more shared records with the interfaceillustrated in FIG. 3 and/or a similar interface.

The entry of the data into the database by a tenant may trigger sharingof the data with another tenant. For example, a trigger may be writtento ensure that the data is replicated and/or synchronized for anothertenant. An example of pseudocode for a trigger is, as follows:

trigger MY_CUSTOM_TRIGGER ON CASE (after insert) { for( Integer i=0; i <Trigger.size; i++) { Case myNewCase = Trigger.new[i]; if (... <somecondition is met>...) { PartnerNetworkRecordConnection newrecord = newPartnerNetworkRecordConnection( ); newrecord.ConnectionId = <hard codedconnection id> newrecord.LocalRecordId = myNewCase.id;newrecord.RelatedRecords = ‘Case’; insert newrecord; // This will sharemy newly created cases with other org. } }

In the example of the pseudocode for a trigger, upon entry of new datato a shared record in the database for a first tenant, a new record maybe created in accordance with the connection between the tenants. Thenew record may have an id for the connection (e.g.newrecord.ConnectionId), the first tenant record id(newrecord.LocalRecordId), and indicate an entity type for the record(e.g. newrecord.RelatedRecords=‘Case’). The “newrecord” in the examplemay be a Case entity type. In a preferred embodiment, a Case entity typemay be available as both a parent and/or a child record for relatedrecords. For example, an Account record may have a child Case record andthe Case record may itself have a child Case record.

If the data entered does not involve shared data in accordance with theconnection (404), then the entered data may not be shared.Alternatively, if the data does involve shared data (404), then mappinginformation for the first tenant and second tenant may be retrieved(406).

Continuing with FIG. 4, the attributes/columns of the shared record of afirst tenant may be mapped to columns for a record at the second tenant(406). A mapping table may be used to map the columns of a record forthe first tenant to columns of a record for the second tenant. Forexample, the second tenant record that is shared with the first tenantrecord may have a column with a foreign key for the corresponding firsttenant record. In another example, the first tenant may have a columnthat is a varchar that is a different size than the respective column ofthe shared record in the second tenant database, and the mapping tablemay keep information on the different types and sizes of the columns forthe tenants to ensure that the information is replicated andsynchronized properly.

The mapping table may be used as a guide for creating new records and/oradding to existing records at the second tenant to replicate the data.For example, the mapping table may be used to create a new shared recordfor the second tenant and the permitted shared information from thetable for the shared record at the first tenant may be assigned tocolumns of a record for a table at the second tenant.

The data for the shared record may be sent to the second tenant (408). Anew record or an existing record at the second tenant may be populatedwith the received data at the first tenant. In one or more embodiments,a notice of a request to replicate and/or synchronize the received dataat the first tenant to the second tenant may be placed on a queue. Abackground process for the on-demand database service may process thenotices on the queue nearly instantaneously after placement on thequeue.

Embodiments of the notice may include, but are not limited to, aninstance of a new record for the second tenant with the received data, adata structure with the received data, one or more keys for the firsttenant record being replicated or synchronized and/or the second tenantrecord, and/or any other information to communicate the need toreplicate and/or synchronize data. The queue may have implementationsincluding, but not limited to, a table, a list, and/or any other datastructure for processing notices to process the received data. In apreferred embodiment, the queue may be a table with fleeting recordsthat are removed as the records for the replicated/synchronized data isprocessed.

Next, a determination is made as to whether the received data for theshared record includes a file attachment (410). For example, a file maybe associated with the shared record with a file name and file path asan attribute/column value for the shared record. If there is noattachment associated with the shared record (410), then a determinationmay be made as to whether the shared record has a relationship toanother record (414). Alternatively, if the shared record includes anattachment (410), then the data from the attachment may be sent to thesecond tenant (412).

The data from the attachment may be copied and placed in a record forthe shared tenant. Similar to the data for the shared record, a noticemay be placed on the queue for the data of the attachment to bereplicated and/or synchronized at the second tenant. Alternatively, thefile itself may be copied and shared with the second tenant.

The attachment associated with the record at the first tenant may beassociated with a corresponding record at the second tenant. In apreferred embodiment, the contents of the file may be placed in a newrecord and the new record may associated with the shared record for thesecond tenant as a child record.

The connection for the tenants may indicate whether the shared data maybe edited at both the first tenant and the second tenant after it hasbeen shared. For example, the first tenant may retain write accessrights to the shared records and may only permit the second tenant toread the shared data. Alternatively, the second tenant may be permittedto write to the shared data, and associate records to the shared data.For example, second tenant may be able to associate Notes and/or fileattachments to a Case that is shared.

A determination may be made as to whether the shared data has relatedrecords (414). If there are no related records (414), then processingfor the entered shared data may end. Alternatively, if there are relatedrecords (414), then a notification may be sent to the first tenant(416). The notification may be sent to the first tenant to request toshare the related record and/or indicate that the related record isshared with the second tenant (416). Next, connection information forthe first and second tenant may be retrieved (402). If the connectiondoes not indicate that the related records may be shared, then anotification may be sent to the first tenant and/or the second tenant toallow for sharing of the related records for the shared data.

FIG. 5A illustrates an example of a user interface for sharinginformation between tenants in a multi-tenant database system. FIG. 5Aprovides a user interface for a Case/Comment record of a first tenantthat may be shared with a second tenant. The example of the userinterface in FIG. 5A provides an interface for editing the Case Comment500 record. The user interface provides the ability to ‘Save’ the recordin the database, ‘Cancel’ editing the record, ‘Spell Check’ for therecord, indicate whether the record is ‘Private’ 502, enter a ‘CaseDescription’ for the Case record, and enter the ‘Comment’ for a Case.

In an embodiment, the history of sharing for a Case and the assignmentof the Case to connections may be displayed on a user interface for eachindividual Case and/or Case/Comment user interface. For example, CaseComments (e.g. 1-0001 “Widget Order Correction” Comment) related to theCase (e.g. Case 1) may be displayed with the Case/Comment Entryinterface and the status of the Case Comment (e.g. Shared withConnection 1) may be displayed. The Case/Comment user interface mayallow for ‘Stop Sharing’ the Case and/or Case/Comments with a connection(e.g. “Connection 1”) for the first tenant.

The Case/Comment user interface may allow a user to ‘Forward Case’ andindividually assign a connection to a case to share the record. The usermay be able to manage the connections for the particular case and assignthe case to one or more connections for forwarding the case to aconnection. In an embodiment, the connections may be managed for theCase with a user interface illustrated in FIG. 3B.

In an embodiment, a Note or Attachment may be associated with the Case.For example, a Note or Attachment may be assigned as related record to aCase (e.g. a child record of a Case). The user may use an interface asillustrated in FIGS. 2A and 2B to input a Note or Attachment for arelated Case. The Note or Attachment from a first tenant may then beforward with a Case to a second tenant in accordance with a connectionif the user selects to forward related records or child records of theCase.

FIG. 5B illustrates an example of a user interface for sharinginformation between tenants in a multi-tenant database system. In one ormore embodiments, a user may elect to automatically accept sharedrecords and related records of shared records. If the user chooses toautomatically accept shared records, then a new record that replicatesthe shared record at the first tenant may be inserted into the databaseof the second tenant with a similar hierarchy as found at the firsttenant.

In another embodiment, the second tenant may select to accept eachrecord as it is received. FIG. 5B allows a user of the second tenant toassign relationships to other records, assign owners, and/or assign theforwarded shared record to a connection. FIG. 5B illustrates an exampleof assigning relationships 506 and owners 504 to Cases by the secondtenant. When a second tenant prefers to accept each record individually,then the user may select how the record is related records at theirdatabase. For example, a Contact or any other user may be assigned as anowner of the Case. In another embodiment, a case may have an assignmentrule that associates the case with a connection. The case may beforwarded to one or more tenants identified for a connection. Relatedrecords may be assigned to the Case, such as, but not limited to,Accounts, Contacts, Assets, and/or a user.

FIG. 5C illustrates an example of a user interface for sharinginformation between tenants in a multi-tenant database system. In anembodiment, the cases may be forwarded to connections ‘en masse’ asillustrated in FIG. 5C. As shown in FIG. 5C, ‘Case 1’ and ‘Case 2’ maybe selected and forwarded to connections by selecting ‘Forward Cases toConnections.’ In an embodiment, ‘Forward Cases to Connections’ may allowa user to navigate to a user interface for connection management; anexample is shown in FIG. 3, to select a connection for sharing theselected cases. The user may select a connection for one or more recordsusing an interface similar to the interface illustrated in FIG. 5C.

FIG. 5D illustrates an example of a user interface for sharinginformation between tenants in a multi-tenant database system. FIG. 5Dillustrates an example of allowing a user of a second tenant database toaccept shared records and/or attachments from the first tenant. As shownin FIG. 5D, ‘Connection 1’ and ‘Connection 2’ may be selected andaccepted by the user of the second tenant database with ‘AcceptConnections.’ Upon acceptance, the shared records may be inserted intorecords for access by the second tenant. In an embodiment, mappingtables may be used to map attributes of shared records from the firsttenant to attributes of shared records at the second tenant. The mappingtables may also indicate how records with the contents of fileattachments may be inserted into tables at the second tenant database.

Although examples may be shown referencing specific records (e.g. Cases,Comments, etc.), those with skill in the art will recognize that theimplementations illustrated in the examples may be used for any type ofdatabase record or data that is to be shared.

Cases and Comments

Case Management may provide the ability to share entity data types, suchas Cases, Comments, Assets, and Attachments. An entity may be a tablefor any type of record or collection of data. A record may be designatedas connected between a first tenant and a second tenant. A Case may berelated to another record. Cases may be shared (e.g. forwarded)individually, in conjunction with other cases (e.g. en masse), and/or inconjunction with a related record (e.g. a child/parent or otherhierarchical relationship with another record such as an Account, aContact, a Product or any other type of entity record in which the casemay be related). Optionally, an application programming interface (API)and/or user interface may include, but is not limited, publish fields,subscribe fields, templates, publish object/field selection, casehistory, indication of connections, a case number field (e.g. a fieldgenerated when the case is created), and/or a forwarding field. Forexample, a Case Number may be a read only field that may be generatedwhen the case is created. Based on an API definition, an example ofbehavior for a Case Number field may be: (a) Publish Field: should beable to publish the Case Number, (b) Subscribe Field: cannot subscribeto Case Number (though the customer may map the connections Case Numberto a Text field (>=80)), and/or (c) the Case Number may be an editablefield.

Cases may be shared in ways including, but not limited to, when a caseis a member of the parent record (e.g. Account/Contact), individually oren-masse using the ‘Forward to Connections’ link on the Case list view.When sharing a case, an email notification may optionally be sent to oneor more users. For example, if a customer shares a case with an emailnotification, a connection owner in the partner's organization mayreceive the email. A partner owner may be one or more individuals/usersthat receive information on the connection between a first and secondtenant. In another example, if a case is shared as a child of anotherrecord and the ‘Send Notification Email’ option is selected, then thenotification may be sent to the ‘Case Owner’ in a subscriber's/user'sorganization. Optionally, the record owner of a first tenant may beprovided a notification when a record is shared with a second tenant.When sharing a case, once the case is accepted, all ‘Public’ comments onthe case at the first tenant may also be shared with the second tenant.‘Public’ comments may be provided for the various methods of sharingcases (e.g. manual, automated, queue assignment). For example, caseforwarding/stop sharing may be managed with the API (e.g. using aPartnerNetworkRecordConnection table).

Forward Cases as Child of Another Record (e.g. Account, Contact, Productand any other Object where the Case is a Related List)

Cases may be forwarded with a related list and/or in accordance with ahierarchical relationship. Although examples are provided of forwardingwith a related list and hierarchical relationship, those skilled in theart will recognize other relationships that may allow for forwarding ofcases. Users may indicate relationships/hierarchicalrelationships/connections with the use of a user interface. For example,if a case is shared as a parent and if the subscriber has not selectedthe ‘Auto-Accept’ option, then the subscriber may accept the Case usingthe ‘Cases from Connections’ list view. This view may include, but isnot limited to, the following fields: Connection Name, Sent Date,Subject, Case Number, Account Name, Contact Name, Priority, Case Status,Asset Name, Parent Record Name and/or Case Type. Continuing with theexample, a Parent Record Name field may be set if the Case is shared asa child of another record and is populated with the name of the parentrecord including type of object (e.g. Account: Acme). A customer maycreate multiple object views using the fields above and assign the sameviews to multiple internal users using a role assignment.

In another example, case reports may be created. Using such reportscustomers may view which cases have been shared and updated by aconnection. Case History and Case reports may have an additional sectionfor Connections (e.g. ‘Connection’ and ‘Connection History’ tables).Validation rules may be utilized for sharing between connections. Forexample, a Customer can use Received Connection Name/ID along with“Current User Alias contains pnet” to ignore validation rules (e.g. whenthe case is shared with a connection (same as other objects)).Optionally, a customer can use Received Connection Name and “CurrentUser contains pnet” to run workflow rules (e.g. rules that are the samewith other objects). List views may be created. For example, ReceivedConnection Name and Sent Connection Name are available to create filterlist views to show all cases shared with one or more connections.Assignment rules may be used to determine case receipt. For example,when a case is assigned to a queue where the connection is a member,then that connection may receive the case. Escalation rules may beapplied to determine how cases are shared. For example, when a case isinserted/updated and is assigned to a queue where a connection is amember, then the connection should receive the case. The API may providethe ability for customers to run triggers on cases using database tables(e.g. PartnerNetworkConnection and PartnerNetworkRecordConnectiontables).

Comments

Comments may be associated/related/connected to a case and sharedaccordingly. For example, comments may be shared if designated a childof a case. Comments may be considered Public (e.g. available to bothinternal and external users) and Private (e.g. only available tointernal users). Comments may have publish and subscribe fields, and mayoptionally use templates. General Forward/Stop Sharing rules may becreated and applied with comments. In an example, when the case isshared, only public comments are forwarded if the Comments object issubscribed by the target connection. If a ‘Private’ or new comment on ashared case is marked ‘Public’, then the comment may automatically beshared with all the connections on the parent case if the connectionshave subscribed to the Comments object.

A stop may be placed on sharing comments. If a comment has already beenshared then the ways to ‘stop sharing’ may include, but are not limitedto, the following steps: (a) If sharing is terminated on the case with aspecific connection, then an implementation may stop sharing anycomments on the case with that specific connection. This stop may notimpact sharing with other active connections on the case. (b) casesand/or comments object that are not published/subscribed to mayautomatically terminate sharing on the comments (c) if a comment that isshared is marked ‘Private’, then sharing may be terminated with all theconnections automatically. Public comments may be forwarded with casesif Comments have been published/subscribed with the connection.

Cases with Comments reports may be modified to include ‘ConnectionHistories’ and ‘Connections’ table. Workflow rules may be used todetermine sharing of comments.

Notes & Attachments

Notes and Attachments may be shared between tenants in a multi-tenantdatabase system. Notes & Attachments may be shared as a ‘child’ of othersupported objects including, but not limited to, the following: Leads,Opportunities, Accounts, Contacts, Products, Cases and Custom Objects.Optionally, an application programming interface (API) and/or userinterface may include, but is not limited, publish fields, subscribefields, templates, publish object/field selection, case history,indication of connections, a case number field (e.g. a field generatedwhen the case is created), and/or a forwarding field. Public Notes andAttachments may be shared with connections with a parent record if theconnection has subscribed to Notes and Attachments. User interfaces mayhave checkbox fields for attachments, such as a ‘Share with Connections’checkbox. The attachment may be visible on edit and detail screen,visible if a parent record is shared, visible if attachment public andthe user is associated with an organization for which the attachment isvisible.

In an example, the steps to share Notes and Attachments include, but arenot limited to, the following: (a) when an Attachment is created bydefault, it is Public (e.g. the Private option is unchecked), (b) thenew attachment may not be shared even if the parent has been shared, (c)the user may edit the attachment and check the ‘Share with Connections’option to enable sharing. In another example, in the targetorganization, the attachment will be marked ‘Public’ and ‘Share withConnections’=true to enable sharing.

Notes may be created by default as Private (e.g. the Public option isunchecked) which means that if the parent has been shared with one ormore connections, then the Notes may not be shared unless the note ismade ‘Public.’ For a private Note/Attachment, if the ‘Private’ option isunchecked (e.g. now public), then the Note may automatically be sharedif subscribed to by the connection (e.g. and parent is shared). In anexample, if the ‘Private’ option is unchecked (e.g. now public) and the‘Share with Connections’ option is checked, then the attachment mayautomatically be shared if subscribed to by the connection (and parentis shared). Sharing ‘Public’ Notes/Attachments may be designated via apior using queues. Child Public Notes/Attachments may be shared whensharing parent record. Public notes may automatically be inserted intotarget organization. Attachments may be shared if the ‘Share withConnections’ checkbox is marked ‘true’ on all ‘Public’ attachments.

Steps to stop sharing Notes/Attachments may include, but are not limitedto, the following: (a) if the ‘Private’ option is selected, then sharingmust be terminated automatically with all connections. The ‘Share withConnections’ checkbox may be set to ‘false’ when the Attachment ismarked private, (b) if the ‘Share with Connections’ checkbox isunchecked on a Public (shared) attachment, then sharing may beterminated immediately with the target organization. If the ‘Public’option is unchecked for notes, then sharing may be terminatedautomatically with all connections. If the Note/Attachment is deleted,then sharing may be terminated automatically with all connections. Forcustom objects, if the ‘Note and Attachment’ option is not selected onthe subscribing organization, then the Public Note/Attachment may not beshared. If sharing on the parent record is terminated either with one ormore connections, then sharing on the Note/Attachment may also beterminated. If a Note/Attachment is Unpublished and Unsubscribed, thensharing may be terminated automatically.

System Overview

FIG. 6 illustrates a block diagram of an environment 610 wherein anon-demand database service might be used. Environment 610 may includeuser systems 612, network 614, system 616, processor system 617,application platform 18, network interface 620, tenant data storage 622,system data storage 624, program code 626, and process space 628. Inother embodiments, environment 610 may not have all of the componentslisted and/or may have other elements instead of, or in addition to,those listed above.

Environment 610 is an environment in which an on-demand database serviceexists. User system 612 may be any machine or system that is used by auser to access a database user system. For example, any of user systems612 can be a handheld computing device, a mobile phone, a laptopcomputer, a work station, and/or a network of computing devices. Asillustrated in FIG. 6 (and in more detail in FIG. 7) user systems 612might interact via a network 614 with an on-demand database service,which is system 616.

An on-demand database service, such as system 616, is a database systemthat is made available to outside users that do not need to necessarilybe concerned with building and/or maintaining the database system, butinstead may be available for their use when the users need the databasesystem (e.g., on the demand of the users). Some on-demand databaseservices may store information from one or more tenants stored intotables of a common database image to form a multi-tenant database system(MTS). Accordingly, “on-demand database service 616” and “system 616”will be used interchangeably herein. A database image may include one ormore database objects. A relational database management system (RDMS) orthe equivalent may execute storage and retrieval of information againstthe database object(s). Application platform 618 may be a framework thatallows the applications of system 616 to run, such as the hardwareand/or software, e.g., the operating system. In an embodiment, on-demanddatabase service 16 may include an application platform 18 that enablescreation, managing and executing one or more applications developed bythe provider of the on-demand database service, users accessing theon-demand database service via user systems 612, or third partyapplication developers accessing the on-demand database service via usersystems 612.

The users of user systems 612 may differ in their respective capacities,and the capacity of a particular user system 612 might be entirelydetermined by permissions (permission levels) for the current user. Forexample, where a salesperson is using a particular user system 612 tointeract with system 616, that user system has the capacities allottedto that salesperson. However, while an administrator is using that usersystem to interact with system 616, that user system has the capacitiesallotted to that administrator. In systems with a hierarchical rolemodel, users at one permission level may have access to applications,data, and database information accessible by a lower permission leveluser, but may not have access to certain applications, databaseinformation, and data accessible by a user at a higher permission level.Thus, different users will have different capabilities with regard toaccessing and modifying application and database information, dependingon a user's security or permission level.

Network 614 is any network or combination of networks of devices thatcommunicate with one another. For example, network 614 can be any one orany combination of a LAN (local area network), WAN (wide area network),telephone network, wireless network, point-to-point network, starnetwork, token ring network, hub network, or other appropriateconfiguration. As the most common type of computer network in currentuse is a TCP/IP (Transfer Control Protocol and Internet Protocol)network, such as the global internetwork of networks often referred toas the “Internet” with a capital “I,” that network will be used in manyof the examples herein. However, it should be understood that thenetworks that the one or more implementations might use are not solimited, although TCP/IP is a frequently implemented protocol.

User systems 612 might communicate with system 616 using TCP/IP and, ata higher network level, use other common Internet protocols tocommunicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTPis used, user system 612 might include an HTTP client commonly referredto as a “browser” for sending and receiving HTTP messages to and from anHTTP server at system 616. Such an HTTP server might be implemented asthe sole network interface between system 616 and network 614, but othertechniques might be used as well or instead. In some implementations,the interface between system 616 and network 614 includes load sharingfunctionality, such as round-robin HTTP request distributors to balanceloads and distribute incoming HTTP requests evenly over a plurality ofservers. At least as for the users that are accessing that server, eachof the plurality of servers has access to the MTS′ data; however, otheralternative configurations may be used instead.

In one embodiment, system 616, shown in FIG. 6, implements a web-basedcustomer relationship management (CRM) system. For example, in oneembodiment, system 616 includes application servers configured toimplement and execute CRM software applications as well as providerelated data, code, forms, webpages and other information to and fromuser systems 612 and to store to, and retrieve from, a database systemrelated data, objects, and Webpage content. With a multi-tenant system,data for multiple tenants may be stored in the same physical databaseobject, however, tenant data typically is arranged so that data of onetenant is kept logically separate from that of other tenants so that onetenant does not have access to another tenant's data, unless such datais expressly shared. In certain embodiments, system 616 implementsapplications other than, or in addition to, a CRM application. Forexample, system 16 may provide tenant access to multiple hosted(standard and custom) applications, including a CRM application. User(or third party developer) applications, which may or may not includeCRM, may be supported by the application platform 618, which managescreation, storage of the applications into one or more database objectsand executing of the applications in a virtual machine in the processspace of the system 616.

One arrangement for elements of system 616 is shown in FIG. 6, includinga network interface 620, application platform 618, tenant data storage622 for tenant data 623, system data storage 624 for system data 625accessible to system 616 and possibly multiple tenants, program code 626for implementing various functions of system 616, and a process space628 for executing MTS system processes and tenant-specific processes,such as running applications as part of an application hosting service.Additional processes that may execute on system 616 include databaseindexing processes.

Several elements in the system shown in FIG. 6 include conventional,well-known elements that are explained only briefly here. For example,each user system 612 could include a desktop personal computer,workstation, laptop, PDA, cell phone, or any wireless access protocol(WAP) enabled device or any other computing device capable ofinterfacing directly or indirectly to the Internet or other networkconnection. User system 612 typically runs an HTTP client, e.g., abrowsing program, such as Microsoft's Internet Explorer browser,Netscape's Navigator browser, Opera's browser, or a WAP-enabled browserin the case of a cell phone, PDA or other wireless device, or the like,allowing a user (e.g., subscriber of the multi-tenant database system)of user system 612 to access, process and view information, pages andapplications available to it from system 616 over network 614. Each usersystem 612 also typically includes one or more user interface devices,such as a keyboard, a mouse, trackball, touch pad, touch screen, pen orthe like, for interacting with a graphical user interface (GUI) providedby the browser on a display (e.g., a monitor screen, LCD display, etc.)in conjunction with pages, forms, applications and other informationprovided by system 616 or other systems or servers. For example, theuser interface device can be used to access data and applications hostedby system 616, and to perform searches on stored data, and otherwiseallow a user to interact with various GUI pages that may be presented toa user. As discussed above, embodiments are suitable for use with theInternet, which refers to a specific global internetwork of networks.However, it should be understood that other networks can be used insteadof the Internet, such as an intranet, an extranet, a virtual privatenetwork (VPN), a non-TCP/IP based network, any LAN or WAN or the like.

According to one embodiment, each user system 612 and all of itscomponents are operator configurable using applications, such as abrowser, including computer code run using a central processing unitsuch as an Intel Pentium® processor or the like. Similarly, system 616(and additional instances of an MTS, where more than one is present) andall of their components might be operator configurable usingapplication(s) including computer code to run using a central processingunit such as processor system 617, which may include an Intel Pentium®processor or the like, and/or multiple processor units. A computerprogram product embodiment includes a machine-readable storage medium(media) having instructions stored thereon/in which can be used toprogram a computer to perform any of the processes of the embodimentsdescribed herein. Computer code for operating and configuring system 16to intercommunicate and to process webpages, applications and other dataand media content as described herein are preferably downloaded andstored on a hard disk, but the entire program code, or portions thereof,may also be stored in any other volatile or non-volatile memory mediumor device as is well known, such as a ROM or RAM, or provided on anymedia capable of storing program code, such as any type of rotatingmedia including floppy disks, optical discs, digital versatile disk(DVD), compact disk (CD), microdrive, and magneto-optical disks, andmagnetic or optical cards, nanosystems (including molecular memory ICs),or any type of media or device suitable for storing instructions and/ordata. Additionally, the entire program code, or portions thereof, may betransmitted and downloaded from a software source over a transmissionmedium, e.g., over the Internet, or from another server, as is wellknown, or transmitted over any other conventional network connection asis well known (e.g., extranet, VPN, LAN, etc.) using any communicationmedium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as arewell known. It will also be appreciated that computer code forimplementing embodiments can be implemented in any programming languagethat can be executed on a client system and/or server or server systemsuch as, for example, C, C++, HTML, any other markup language, Java™,JavaScript, ActiveX, any other scripting language, such as VBScript, andmany other programming languages as are well known may be used. (Java™is a trademark of Sun Microsystems, Inc.).

According to one embodiment, each system 616 is configured to providewebpages, forms, applications, data and media content to user (client)systems 612 to support the access by user systems 612 as tenants ofsystem 616. As such, system 616 provides security mechanisms to keepeach tenant's data separate unless the data is shared. If more than oneMTS is used, they may be located in close proximity to one another(e.g., in a server farm located in a single building or campus), or theymay be distributed at locations remote from one another (e.g., one ormore servers located in city A and one or more servers located in cityB). As used herein, each MTS could include one or more logically and/orphysically connected servers distributed locally or across one or moregeographic locations. Additionally, the term “server” is meant toinclude a computer system, including processing hardware and processspace(s), and an associated storage system and database application(e.g., OODBMS or RDBMS) as is well known in the art. It should also beunderstood that “server system” and “server” are often usedinterchangeably herein. Similarly, the database object described hereincan be implemented as single databases, a distributed database, acollection of distributed databases, a database with redundant online oroffline backups or other redundancies, etc., and might include adistributed database or storage network and associated processingintelligence.

FIG. 7 also illustrates environment 610. However, in FIG. 7 elements ofsystem 616 and various interconnections in an embodiment are furtherillustrated. FIG. 7 shows that user system 612 may include processorsystem 612A, memory system 612B, input system 612C, and output system612D. FIG. 7 shows network 614 and system 616. FIG. 7 also shows thatsystem 616 may include tenant data storage 622, tenant data 623, systemdata storage 624, system data 625, User Interface (UI) 730, ApplicationProgram Interface (API) 732, PL/SOQL 734, save routines 736, applicationsetup mechanism 738, applications servers 1000 ₁-1000 _(N), systemprocess space 702, tenant process spaces 704, tenant management processspace 710, tenant storage area 712, user storage 714, and applicationmetadata 716. In other embodiments, environment 610 may not have thesame elements as those listed above and/or may have other elementsinstead of, or in addition to, those listed above.

User system 612, network 614, system 616, tenant data storage 622, andsystem data storage 624 were discussed above in FIG. 6. Regarding usersystem 612, processor system 612A may be any combination of one or moreprocessors. Memory system 612B may be any combination of one or morememory devices, short term, and/or long term memory. Input system 612Cmay be any combination of input devices, such as one or more keyboards,mice, trackballs, scanners, cameras, and/or interfaces to networks.Output system 612D may be any combination of output devices, such as oneor more monitors, printers, and/or interfaces to networks. As shown byFIG. 7, system 616 may include a network interface 620 (of FIG. 6)implemented as a set of HTTP application servers 700, an applicationplatform 618, tenant data storage 622, and system data storage 624. Alsoshown is system process space 702, including individual tenant processspaces 704 and a tenant management process space 710. Each applicationserver 1000 may be configured to tenant data storage 622 and the tenantdata 623 therein, and system data storage 624 and the system data 625therein to serve requests of user systems 612. The tenant data 623 mightbe divided into individual tenant storage areas 712, which can be eithera physical arrangement and/or a logical arrangement of data. Within eachtenant storage area 712, user storage 714 and application metadata 716might be similarly allocated for each user. For example, a copy of auser's most recently used (MRU) items might be stored to user storage714. Similarly, a copy of MRU items for an entire organization that is atenant might be stored to tenant storage area 712. A UI 730 provides auser interface and an API 732 provides an application programmerinterface to system 616 resident processes to users and/or developers atuser systems 612. The tenant data and the system data may be stored invarious databases, such as one or more Oracle™ databases.

Application platform 618 includes an application setup mechanism 738that supports application developers' creation and management ofapplications, which may be saved as metadata into tenant data storage622 by save routines 736 for execution by subscribers as one or moretenant process spaces 704 managed by tenant management process 710 forexample. Invocations to such applications may be coded using PL/SOQL 34that provides a programming language style interface extension to API732. A detailed description of some PL/SOQL language embodiments isdiscussed in commonly owned co-pending U.S. Provisional PatentApplication 60/828,192 entitled, PROGRAMMING LANGUAGE METHOD AND SYSTEMFOR EXTENDING APIS TO EXECUTE IN CONJUNCTION WITH DATABASE APIS, byCraig Weissman, filed Oct. 4, 2006, which is incorporated in itsentirety herein for all purposes. Invocations to applications may bedetected by one or more system processes, which manages retrievingapplication metadata 716 for the subscriber making the invocation andexecuting the metadata as an application in a virtual machine.

Each application server 700 may be communicably coupled to databasesystems, e.g., having access to system data 625 and tenant data 623, viaa different network connection. For example, one application server 700₁ might be coupled via the network 614 (e.g., the Internet), anotherapplication server 700 _(N-1) might be coupled via a direct networklink, and another application server 700 _(N) might be coupled by yet adifferent network connection. Transfer Control Protocol and InternetProtocol (TCP/IP) are typical protocols for communicating betweenapplication servers 700 and the database system. However, it will beapparent to one skilled in the art that other transport protocols may beused to optimize the system depending on the network interconnect used.

In certain embodiments, each application server 700 is configured tohandle requests for any user associated with any organization that is atenant. Because it is desirable to be able to add and remove applicationservers from the server pool at any time for any reason, there ispreferably no server affinity for a user and/or organization to aspecific application server 700. In one embodiment, therefore, aninterface system implementing a load balancing function (e.g., an F5Big-IP load balancer) is communicably coupled between the applicationservers 700 and the user systems 612 to distribute requests to theapplication servers 700. In one embodiment, the load balancer uses aleast connections algorithm to route user requests to the applicationservers 700. Other examples of load balancing algorithms, such as roundrobin and observed response time, also can be used. For example, incertain embodiments, three consecutive requests from the same user couldhit three different application servers 700, and three requests fromdifferent users could hit the same application server 700. In thismanner, system 616 is multi-tenant, wherein system 616 handles storageof, and access to, different objects, data and applications acrossdisparate users and organizations.

As an example of storage, one tenant might be a company that employs asales force where each salesperson uses system 616 to manage their salesprocess. Thus, a user might maintain contact data, leads data, customerfollow-up data, performance data, goals and progress data, etc., allapplicable to that user's personal sales process (e.g., in tenant datastorage 622). In an example of a MTS arrangement, since all of the dataand the applications to access, view, modify, report, transmit,calculate, etc., can be maintained and accessed by a user system havingnothing more than network access, the user can manage his or her salesefforts and cycles from any of many different user systems. For example,if a salesperson is visiting a customer and the customer has Internetaccess in their lobby, the salesperson can obtain critical updates as tothat customer while waiting for the customer to arrive in the lobby.

While each user's data might be separate from other users' dataregardless of the employers of each user, some data might beorganization-wide data shared or accessible by a plurality of users orall of the users for a given organization that is a tenant. Thus, theremight be some data structures managed by system 616 that are allocatedat the tenant level while other data structures might be managed at theuser level. Because an MTS might support multiple tenants includingpossible competitors, the MTS should have security protocols that keepdata, applications, and application use separate. Also, because manytenants may opt for access to an MTS rather than maintain their ownsystem, redundancy, up-time, and backup are additional functions thatmay be implemented in the MTS. In addition to user-specific data andtenant specific data, system 616 might also maintain system level datausable by multiple tenants or other data. Such system level data mightinclude industry reports, news, postings, and the like that are sharableamong tenants.

In certain embodiments, user systems 612 (which may be client systems)communicate with application servers 700 to request and updatesystem-level and tenant-level data from system 616 that may requiresending one or more queries to tenant data storage 622 and/or systemdata storage 624. System 616 (e.g., an application server 700 in system616) automatically generates one or more SQL statements (e.g., one ormore SQL queries) that are designed to access the desired information.System data storage 624 may generate query plans to access the requesteddata from the database.

Each database can generally be viewed as a collection of objects, suchas a set of logical tables, containing data fitted into predefinedcategories. A “table” is one representation of a data object, and may beused herein to simplify the conceptual description of objects and customobjects. It should be understood that “table” and “object” may be usedinterchangeably herein. Each table generally contains one or more datacategories logically arranged as columns or fields in a viewable schema.Each row or record of a table contains an instance of data for eachcategory defined by the fields. For example, a CRM database may includea table that describes a customer with fields for basic contactinformation such as name, address, phone number, fax number, etc.Another table might describe a purchase order, including fields forinformation such as customer, product, sale price, date, etc. In somemulti-tenant database systems, standard entity tables might be providedfor use by all tenants. For CRM database applications, such standardentities might include tables for Account, Contact, Lead, andOpportunity data, each containing pre-defined fields. It should beunderstood that the word “entity” may also be used interchangeablyherein with “object” and “table”.

In some multi-tenant database systems, tenants may be allowed to createand store custom objects, or they may be allowed to customize standardentities or objects, for example by creating custom fields for standardobjects, including custom index fields. U.S. patent application Ser. No.10/817,161, filed Apr. 2, 2004, entitled “Custom Entities and Fields ina Multi-Tenant Database System”, and which is hereby incorporated hereinby reference, teaches systems and methods for creating custom objects aswell as customizing standard objects in a multi-tenant database system.In certain embodiments, for example, all custom entity data rows arestored in a single multi-tenant physical table, which may containmultiple logical tables per organization. It is transparent to customersthat their multiple “tables” are in fact stored in one large table orthat their data may be stored in the same table as the data of othercustomers.

While one or more implementations have been described by way of exampleand in terms of the specific embodiments, it is to be understood thatone or more implementations are not limited to the disclosedembodiments. To the contrary, it is intended to cover variousmodifications and similar arrangements as would be apparent to thoseskilled in the art. Therefore, the scope of the appended claims shouldbe accorded the broadest interpretation so as to encompass all suchmodifications and similar arrangements.

1. A method of sharing information between tenants in a multi-tenantdatabase, the method comprising: receiving information on a connectionbetween a first tenant of a multi-tenant database and a second tenant,wherein the connection comprises information on a scope of data from thefirst tenant shared with the second tenant; allowing data for a recordof the first tenant to be accessible to the second tenant in accordancewith the connection; receiving information on a file related to therecord of the first tenant; and allowing data from the file to beaccessible to the second tenant in accordance with the connection. 2.The method of claim 1, the method further comprising: receiving data forthe record of the first tenant; and retrieving information on theconnection upon entry of the data for the record of the first tenant inthe multi-tenant database.
 3. The method of claim 1, wherein the recordcomprises at least one of a case, a note, an attachment, and a comment.4. The method of claim 1, the method further comprising: retrievingmapping information for one or more columns in a database table for thefirst tenant to one or more columns in a database table for the secondtenant; creating a shared record for the second tenant with mappinginformation; and sending a request to enter the shared record into thedatabase table for the second tenant.
 5. The method of claim 1, themethod further comprising: receiving information on a related record tothe record for the first tenant; and sending a request to enter datafrom the related record in a database table for the second tenant inaccordance with the connection.
 6. The method of claim 5, wherein therelated record is a parent record.
 7. The method of claim 4, wherein theshared record comprises the data from the file.
 8. A computer-readablestorage medium having one or more instructions thereon for sharinginformation between tenants in a multi-tenant database, the instructionswhen executed by one or more processors causing the one or moreprocessors to carry out: receiving information on a connection between afirst tenant of a multi-tenant database and a second tenant, wherein theconnection comprises information on a scope of data from the firsttenant shared with the second tenant; allowing data for a record of thefirst tenant to be accessible to the second tenant in accordance withthe connection; receiving information on a file related to the record ofthe first tenant; and allowing data from the file to be accessible tothe second tenant in accordance with the connection.
 9. Thecomputer-readable storage medium of claim 8, the instructions whenexecuted by one or more processors causing the one or more processors tofurther carry out: receiving data for the record of the first tenant;and retrieving information on the connection upon entry of the data forthe record of the first tenant in the multi-tenant database.
 10. Thecomputer-readable storage medium of claim 8, wherein the recordcomprises at least one of a case, a note, an attachment, and a comment.11. The computer-readable storage medium of claim 8, the instructionswhen executed by one or more processors causing the one or moreprocessors to further carry out: retrieving mapping information for oneor more columns in a database table for the first tenant to one or morecolumns in a database table for the second tenant; creating a sharedrecord for the second tenant with mapping information; and sending arequest to enter the shared record into the database table for thesecond tenant.
 12. The computer-readable storage medium of claim 8, theinstructions when executed by one or more processors causing the one ormore processors to further carry out: receiving information on a relatedrecord to the record for the first tenant; and sending a request toenter data from the related record in a database table for the secondtenant in accordance with the connection.
 13. The computer-readablestorage medium of claim 12, wherein the related record is a parentrecord.
 14. The computer-readable storage medium of claim 11, whereinthe shared record comprises the data from the file.
 15. A system foroptimizing a query in a database system, the system comprising: aprocessor; and one or more stored sequences of instructions which, whenexecuted by the processor, cause the processor to carry out: receivinginformation on a connection between a first tenant of a multi-tenantdatabase and a second tenant, wherein the connection comprisesinformation on a scope of data from the first tenant shared with thesecond tenant; allowing data for a record of the first tenant to beaccessible to the second tenant in accordance with the connection;receiving information on a file related to the record of the firsttenant; and allowing data from the file to be accessible to the secondtenant in accordance with the connection.
 16. The system of claim 15,the instructions when executed by the processor causing the processor tofurther carry out: receiving data for the record of the first tenant;and retrieving information on the connection upon entry of the data forthe record of the first tenant in the multi-tenant database.
 17. Thesystem of claim 15, wherein the record comprises at least one of a case,a note, an attachment, and a comment.
 18. The system of claim 15, theinstructions when executed by the processor causing the processor tofurther carry out: retrieving mapping information for one or morecolumns in a database table for the first tenant to one or more columnsin a database table for the second tenant; creating a shared record forthe second tenant with mapping information; and sending a request toenter the shared record into the database table for the second tenant.19. The system of claim 15, the instructions when executed by theprocessor causing the processor to further carry out: receivinginformation on a related record to the record for the first tenant; andsending a request to enter data from the related record in a databasetable for the second tenant in accordance with the connection.
 20. Thesystem of claim 19, wherein the related record is a parent record.